20241 0 false 2009-03-18T17:03:29-05:00 48348 44 undefined-method-fixtures 43 15332 new 2009-04-05T07:52:28-05:00 48348 Jeff Schwab Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 The tests installed by restful_authentication encounter undefined-method errors, starting with "undefined method `fixtures'" for the unit tests. The problem seems to be that the tests derive only from Test::Unit::TestCase, whereas the relevant methods are defined in ActiveRecord::TestCase and ActionController::TestCase for unit and functional tests, respectively. My current work-around is to change the base class by hand, e.g. to replace class UserTest < Test::Unit::TestCase with class UserTest < ActiveRecord::TestCase This addresses the error, so that the tests at least can run. The tests installed by restful_authentication encounter undefined-method errors, starting with "undefined method `fixtures'" for the unit tests. The problem seems to be that the tests derive only from Test::Unit::TestCase, whereas the relevant methods are defined in ActiveRecord::TestCase and ActionController::TestCase for unit and functional tests, respectively. My current work-around is to change the base class by hand, e.g. to replace class UserTest < Test::Unit::TestCase with class UserTest < ActiveRecord::TestCase This addresses the error, so that the tests at least can run. <div><p>The tests installed by restful_authentication encounter undefined-method errors, starting with "undefined method <code>fixtures'" for the unit tests. The problem seems to be that the tests derive only from Test::Unit::TestCase, whereas the relevant methods are defined in ActiveRecord::TestCase and ActionController::TestCase for unit and functional tests, respectively.</code></p> <p>My current work-around is to change the base class by hand, e.g. to replace</p> <pre> <code>class UserTest &lt; Test::Unit::TestCase </code> </pre> <p>with</p> <pre> <code>class UserTest &lt; ActiveRecord::TestCase </code> </pre> <p>This addresses the error, so that the tests at least can run.</p></div> 20241 0 The tests installed by restful_authentication encounter undefined-method errors, starting with "undefined method `fixtures'" for the unit tests. The problem seems to be that the tests derive only from Test::Unit::TestCase, whereas the relevant methods are defined in ActiveRecord::TestCase and ActionController::TestCase for unit and functional tests, respectively. My current work-around is to change the base class by hand, e.g. to replace class UserTest < Test::Unit::TestCase with class UserTest < ActiveRecord::TestCase This addresses the error, so that the tests at least can run. <div><p>The tests installed by restful_authentication encounter undefined-method errors, starting with "undefined method <code>fixtures'" for the unit tests. The problem seems to be that the tests derive only from Test::Unit::TestCase, whereas the relevant methods are defined in ActiveRecord::TestCase and ActionController::TestCase for unit and functional tests, respectively.</code></p> <p>My current work-around is to change the base class by hand, e.g. to replace</p> <pre> <code>class UserTest &lt; Test::Unit::TestCase </code> </pre> <p>with</p> <pre> <code>class UserTest &lt; ActiveRecord::TestCase </code> </pre> <p>This addresses the error, so that the tests at least can run.</p></div> false 2009-03-18T17:03:29-05:00 48348 --- {} 44 undefined-method-fixtures 0 15332 new 2009-03-18T17:03:32-05:00 48348 Jeff Schwab Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 20241 0 You don't know me but... I'm working on some Rails 2.0-compliant stuff to get the code working with Rails 2.3.2 (which I'm using at work). I've made a fork of the repo for this. When I'm done I'll make a pull-request. My plan is to add another command-line option "--two-point-oh" that will switch on the 2.0-style things (eg rm fixtures and ids, and using "test do" instead of "def test_"). Right now I'm not sure if this option should be "on" or "off" by default. whatcha think? Taryn <div><p>You don't know me but... I'm working on some Rails 2.0-compliant stuff to get the code working with Rails 2.3.2 (which I'm using at work).</p> <p>I've made a fork of the repo for this. When I'm done I'll make a pull-request.</p> <p>My plan is to add another command-line option "--two-point-oh" that will switch on the 2.0-style things (eg rm fixtures and ids, and using "test do" instead of "def test_").</p> <p>Right now I'm not sure if this option should be "on" or "off" by default.</p> <p>whatcha think?</p> <p>Taryn</p></div> false 2009-03-30T09:40:07-05:00 48348 --- :title: undefined method `fixtures' 44 undefined-method-fixtures 0 15332 new 2009-03-30T09:40:11-05:00 51760 Taryn East Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 20241 0 Hmmm - just thinking - if you were able to just remove 'fixtures', perhaps there should be no backwards-compatibility at all. Is there not some sort of "RA Classic" for that sort of thing? Just curious... it'd make my life much easier... Cheers, Taryn <div><p>Hmmm - just thinking - if you were able to just remove 'fixtures', perhaps there should be no backwards-compatibility at all. Is there not some sort of "RA Classic" for that sort of thing?</p> <p>Just curious... it'd make my life much easier...</p> <p>Cheers, Taryn</p></div> false 2009-03-30T09:56:39-05:00 48348 --- {} 44 undefined-method-fixtures 0 15332 new 2009-03-30T09:56:40-05:00 51760 Taryn East Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 20241 0 I see the same problem with 2.3 and 2.0, so I'm not sure what the flag would do. It's not just 'fixtures'; if you remove that, other errors occur later in the file. <div><p>I see the same problem with 2.3 and 2.0, so I'm not sure what the flag would do. It's not just 'fixtures'; if you remove that, other errors occur later in the file.</p></div> false 2009-03-31T18:05:10-05:00 48348 --- {} 44 undefined-method-fixtures 0 15332 new 2009-03-31T18:05:12-05:00 48348 Jeff Schwab Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 20241 0 How and why did you change the name of the ticket? This is not a 2.0-specific issue; in fact, I don't see how it's version-specific at all. I think you'll have better luck if you change the name back, and open a new ticket. <div><p>How and why did you change the name of the ticket? This is not a 2.0-specific issue; in fact, I don't see how it's version-specific at all. I think you'll have better luck if you change the name back, and open a new ticket.</p></div> false 2009-04-01T11:42:31-05:00 48348 --- {} 44 undefined-method-fixtures 0 15332 new 2009-04-01T11:42:35-05:00 48348 Jeff Schwab Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 20241 0 Restoring a title that matches the error message, so other victims will be able to find this ticket more easily. <div><p>Restoring a title that matches the error message, so other victims will be able to find this ticket more easily.</p></div> false 2009-04-01T11:43:48-05:00 48348 --- :title: 2.0-non-compliant 44 undefined-method-fixtures 0 15332 new 2009-04-01T11:43:52-05:00 48348 Jeff Schwab Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44 20241 0 This problem appears to be fixed in http://github.com/technoweenie/restful-authentication.git/ The version with the problem is still online at: http://svn.techno-weenie.net/projects/plugins/restful_authentication/ <div><p>This problem appears to be fixed in <a href="http://github.com/technoweenie/restful-authentication.git/">http://github.com/technoweenie/r...</a></p> <p>The version with the problem is still online at: <a href="http://svn.techno-weenie.net/projects/plugins/restful_authentication/"> http://svn.techno-weenie.net/pro...</a></p></div> false 2009-04-05T07:52:27-05:00 48348 --- {} 44 undefined-method-fixtures 0 15332 new 2009-04-05T07:52:28-05:00 48348 Jeff Schwab Jeff Schwab mrflip http://rails_security.lighthouseapp.com/projects/15332/tickets/44